|
Defining the sprint's goal
At the beginning of the first sprints of the first release of a product, the goal is usually to show the feasability on
the potential architecture.
Then, once the architecture is validated, the goal of a sprint is proposed by the Product Owner and discussed
with the team. It oftenly focuses on a given functional theme.
|
Identifying tasks from items
The 2nd part of the meeting is about defining how the team is gonna achieve the sprint objectives.
To do that, each selected Product Backlog Item is decomposed into tasks. This enables the team to discuss and figure solutions aspects towards this
item, asking the procut owner, if necessary, precisions on the product behavior.
Normaly, all the lifecycle activities are rolled out during a sprint:
-
Selected requirements are specified
-
Architecture is modified if necessary
-
Classes and subsystems are designed, implemented and tested
-
The different components are integrated and tested
-
Product is packaged
-
Acceptance tests are passed.
The given importance to these activities depends on the position of the sprint within the release.
The planned work in a previous sprint that couldn't be done because of objectives reduction, becomes the priority for
next sprint.
|
Assigning tasks
Once sprint activities are defined, they will be assigned to team members. Activities can be done by one or many persons.
All the activities must be taken in to account, including work meetings (non Scrum meetings as well), code or document
reviews.
It is preferable to delay assignement of certain activities, which will be assigned during the sprint in accordance with
team members availability. |
Selecting the items
It is about defining the scope of this sprint. This is done by associating Product Backlog Items one by one to the sprint, and balancing with the team velocity.
If a Release planning has been done, this step is only about collectively validating
the forecasted backlog subset for the sprint.
|
Estimating tasks
Tasks are estimated in hours. Tasks should be thin enough to take less than 16 hours.
Estimation is collectively made by the team. During this discussion, technical aspects are reviewed.
|
Getting team commitment
Team should collectively commit to the sprint backlog, that is on backlog items it estimates being able to implement
within the sprint.
|
|
